3 days ago I tried deploying 4 solutions via stsadm. In Central Admin, these solutions still have the status of "deploying". All previously deployed solutions have the status of "deployed".I have tried a reboot but these solutions haven't changed there status in 3 days. What else could I do ????

DayLight Savings Time issue more than likely. Your SP immediate timer jobs are were probably created wrong. There is a patch out for this. Joel's blog discusses this patch at: http://blogs.msdn.com/joelo/archive/2007/10/16/sharepoint-faq-on-dst-and-october-9th-public-update.aspx. Also you can use stsadm -o execAdmSvcJobs to force the job to run.

Thanks Darrin

I have the same problem here in Perth Australia...and can't wait for our SharePoint SP1 rollout to happen. Initially the Windows SharePoint Services Timer was not running when I ran the add solution and deploy solution, so I started it. But it didn't seem to pick up the Jobs. I've tried execadmsvcjobs to force it and it doesn't pick it up. The Jobs are in the Job Definitions as "One-Time" and their is a Last Run time in there also which correlates with when I fired off the stsadm commands. It looks like it's just holding onto the Jobs for some reason. I have tried various things around Cancelling the deployment, which executes properly. But then when I try and retract the solution,it too gets a Job set up and gets stuck also, which means the Solution gets stuck at Retracting! Deleting the Job Timer Definition for some reasons resolves it from saying Deploying or Retracting. I took a further look at this and basically it was because all the servers in the farms Windows SharePoint Services Timer had stopped! I remoteconnected to them all and started them and ran execadmsvcjobs and it all seemed to fix itself up. Thanks Jeremy http://wss.made4the.net/Lists/Posts/Post.aspx?ID=650

My problem was that my solutionwas stuck retracting. While searching for an answer I happened upon this thread. Jeremy mentioned the timer service, so I checked and noticed mine was not even running. The user it runs under had its password changed, so there must have been a logon failure at some point. I changed the credentials and started the service, and was immediately able to retract my solution.

Jeremy Thake said: I took a further look at this and basically it was because all the servers in the farms Windows SharePoint Services Timer had stopped! I remoteconnected to them all and started them and ran execadmsvcjobs and it all seemed to fix itself up.It turned out my issue lay on the app server only. The jobs were completing successfully on the two WFE's but not on the App server. This caused the job to hang in the "deploying" status. Once I started the Timer Job on the App server all the timer jobs completed and the solutions showed up as deployed. MCSE, Web Systems Administrator

Hi, Also check out this link for help on this issue: http://prasanjitmandal.blogspot.com/2010/06/sharepoint-timer-job-stuck-at-deploying.htmlBR, PM

Hi Guys, I am having the same problem..In my server, Sharepoint 2010 Administration and sharepoint 2010 timer job both services are running perfectly but when i tried to retract or update sharepoint solution then it gets stuck for me any solutoin??